-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix data corruption, Port [#18525] to branch-2.10 #18546
Fix data corruption, Port [#18525] to branch-2.10 #18546
Conversation
### What changes are proposed in this pull request? A this fix a bug in corrupted data files. Previously, Alluxio#17497 attempt to solve this issue but only covers the case when creating a UFS reader Notice we only handle block reader. So this may not fix `paged Block Reader` in 2.x ### Why are the changes needed? Please clarify why the changes are needed. For instance, 1. If you propose a new API, clarify the use case for a new API. 2. If you fix a bug, describe the bug. ### Does this PR introduce any user facing changes? Please list the user-facing changes introduced by your change, including 1. change in user-facing APIs 2. addition or removal of property keys 3. webui pr-link: Alluxio#18525 change-id: cid-bbba0feb29231e70750e5e79da5f405bb591d47a
Automated checks report:
Some checks failed. Please fix the reported issues and reply |
8461597
to
aab5259
Compare
Automated checks report:
All checks passed! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
alluxio-bot, merge this please |
merge failed: |
alluxio-bot, merge this please |
What changes are proposed in this pull request?
This fix a bug in corrupted data files.
Previously, #17497 attempt to solve this issue but only covers the case when creating a UFS reader
Notice we only handle block reader. So this may not fix paged Block Reader in 2.x
Why are the changes needed?
Please clarify why the changes are needed. For instance,
If you propose a new API, clarify the use case for a new API.
If you fix a bug, describe the bug.
Does this PR introduce any user facing changes?
Please list the user-facing changes introduced by your change, including
change in user-facing APIs
addition or removal of property keys
[This is an auto-generated PR to cherry-pick committed PR https://github.com//pull/18525 into branch branch-2.10]